|
JIT spraying is a class of computer security exploit that circumvents the protection of address space randomization (ASLR) and data execution prevention (DEP) by exploiting the behavior of just-in-time compilation. It has been reported to have been used to penetrate security features in the PDF format and Adobe's Flash technology. A just-in-time compiler (JIT) by definition produces code as its data. Since the purpose is to produce executable data, a JIT compiler is one of the few types of programs that cannot be run in a no-executable-data environment. Because of this, JIT compilers are normally exempt from data execution prevention. A JIT spray attack does heap spraying with the generated code. To produce exploit code from JIT, an idea from Dion Blazakis〔(【引用サイトリンク】url=http://www.semantiscope.com/research/BHDC2010/BHDC-2010-Paper.pdf ); 〕 is used. The input program, typically JavaScript or ActionScript, typically contains numerous constant values that can be erroneously executed as code. For example, the XOR operation could be used:〔(Writing JIT-Spray Shellcode for fun and profit ), Alexey Sintsov, (pdf)〕 var a = (0x11223344^0x44332211^0x44332211^ ...); JIT then will transform bytecode to native x86 code like: 0: b8 44 33 22 11 mov $0x11223344,%eax mov eax,0x11223344 5: 35 11 22 33 44 xor $0x44332211,%eax xor eax,0x44332211 a: 35 11 22 33 44 xor $0x44332211,%eax xor eax,0x44332211 The attacker then uses a suitable bug to redirect code execution into the newly generated code. For example, a buffer overflow or use after free bug could allow the attack to modify a function pointer or return address. This causes the CPU to execute instructions in a way that was unintended by the JIT authors. The attacker is usually not even limited to the expected instruction boundaries; it is possible to jump into the middle of an intended instruction to have the CPU interpret it as something else. As with non-JIT ROP attacks, this may be enough operations to usefully take control of the computer. Continuing the above example, jumping to the second byte of the "mov" instruction results in an "inc" instruction: 1: 44 inc %esp inc esp 2: 33 22 xor (%edx),%esp xor esp,DWORD PTR () 4: 11 35 11 22 33 44 adc %esi,0x44332211 adc DWORD PTR ds:0x44332211,esi a: 35 11 22 33 44 xor $0x44332211,%eax xor eax,0x44332211 Computer hardware that allows jumping into the middle of an instruction includes x86, x86-64, and ARM. Although especially effective on this type of hardware, JIT spraying works on other systems as well. To protect against JIT spraying, the JIT code can be disabled or made less predictable for the attacker.〔 == References == 抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』 ■ウィキペディアで「JIT spraying is a class of computer security exploit that circumvents the protection of address space randomization (ASLR) and data execution prevention (DEP) by exploiting the behavior of just-in-time compilation. It has been reported to have been used to penetrate security features in the PDF format and Adobe's Flash technology.A just-in-time compiler (JIT) by definition produces code as its data. Since the purpose is to produce executable data, a JIT compiler is one of the few types of programs that cannot be run in a no-executable-data environment. Because of this, JIT compilers are normally exempt from data execution prevention. A JIT spray attack does heap spraying with the generated code.To produce exploit code from JIT, an idea from Dion Blazakis(【引用サイトリンク】url=http://www.semantiscope.com/research/BHDC2010/BHDC-2010-Paper.pdf ); is used. The input program, typically JavaScript or ActionScript, typically contains numerous constant values that can be erroneously executed as code. For example, the XOR operation could be used:(Writing JIT-Spray Shellcode for fun and profit ), Alexey Sintsov, (pdf)var a = (0x11223344^0x44332211^0x44332211^ ...);JIT then will transform bytecode to native x86 code like: 0: b8 44 33 22 11 mov $0x11223344,%eax mov eax,0x11223344 5: 35 11 22 33 44 xor $0x44332211,%eax xor eax,0x44332211 a: 35 11 22 33 44 xor $0x44332211,%eax xor eax,0x44332211The attacker then uses a suitable bug to redirect code execution into the newly generated code. For example, a buffer overflow or use after free bug could allow the attack to modify a function pointer or return address.This causes the CPU to execute instructions in a way that was unintended by the JIT authors. The attacker is usually not even limited to the expected instruction boundaries; it is possible to jump into the middle of an intended instruction to have the CPU interpret it as something else. As with non-JIT ROP attacks, this may be enough operations to usefully take control of the computer. Continuing the above example, jumping to the second byte of the "mov" instruction results in an "inc" instruction: 1: 44 inc %esp inc esp 2: 33 22 xor (%edx),%esp xor esp,DWORD PTR () 4: 11 35 11 22 33 44 adc %esi,0x44332211 adc DWORD PTR ds:0x44332211,esi a: 35 11 22 33 44 xor $0x44332211,%eax xor eax,0x44332211Computer hardware that allows jumping into the middle of an instruction includes x86, x86-64, and ARM. Although especially effective on this type of hardware, JIT spraying works on other systems as well.To protect against JIT spraying, the JIT code can be disabled or made less predictable for the attacker.== References ==」の詳細全文を読む スポンサード リンク
|